All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

I have read the CLA Document and I hereby sign the CLA

Hi @connyay, following the above fix do you think that the artifact name should also include the scope?

because currently its uploaded without it .
jfrog-cli-tests-=1.0.0.tgz > @scope/jfrog-cli-tests-=1.0.0.tgz

Hi @connyay, following the above fix do you think that the artifact name should also include the scope? because currently its uploaded without it . jfrog-cli-tests-=1.0.0.tgz > @scope/jfrog-cli-tests-=1.0.0.tgz

@connyay

@sverdlov93 I am not sure. I don't think so.

This test case matches my expectations:

From what I can tell this change will fix jfrog/jfrog-cli#2280

Is there a separate issue about the artifact name not having scope?

Following your change, we have failing tests on JFrog CLI, so I am trying to understand how to handle that.
For example:
{
"name": "@my-scope/my-package",
"version": "1.0.0",
"description": "A sample scoped package",
}
The artifact name here should be @my-scope/my-package or my-package ?